Remove stillborn DTD section, in favour of an upcoming new doc for the xm

create DTD.

Signed-off-by: Ewan Mellor <ewan@xensource.com>

diff --git a/docs/xen-api/xenapi-datamodel.tex b/docs/xen-api/xenapi-datamodel.tex
index 4d414e69ba4a44955ab3e5f135d46cbfc0fd475f..e5d2c18400470c7ea982abb6d5aaeae9ee2a4c15 100644 (file)
--- a/docs/xen-api/xenapi-datamodel.tex
+++ b/docs/xen-api/xenapi-datamodel.tex
@@ -13582,14 +13582,3 @@ HVM is required for this operation
 {\bf Signature:}
 \begin{verbatim}VM_HVM_REQUIRED(vm)\end{verbatim}
 \begin{center}\rule{10em}{0.1pt}\end{center}
-
-
-
-\newpage
-\section{DTD}
-General notes:
-\begin{itemize}
-\item Values of primitive types (int, bool, etc) and higher-order types (Sets, Maps) are encoded as simple strings, rather than being expanded into XML fragments. For example ``5'', ``true'', ``1, 2, 3, 4'', ``(1, 2), (2, 3), (3, 4)''
-\item Values of enumeration types are represented as strings (e.g. ``PAE'', ``3DNow!'')
-\item Object References are represented as UUIDs, written in string form
-\end{itemize}